Ability to Override Plan Fields
The ability to override the plan screen fields has the following new behavior of the Field, XML Panes Present in the application for this enhancement
Fields Pane - New Enhancement Behavior- Inherited fields will continue to be presented with a gray background and in the order of their inheritance.
- Element values of a selected inherited field will continue to be presented and disabled in the FieldProperties Window.
- A tool tip displays upon mouse hover over an inherited field. The tool tip contains the product name from which the field was inherited.
- Inherited fields can be copied to the non-inheritance space. All elements and attributes of the duplicated field are copied to the new field except for the name of the field.
- If the configuror wants to reuse the same name in the non-inheritance space, it will be allowed. The condition for unique name should be checked within the non-inheritance space - meaning, within the non-inherited fields, no two fields can have the same name but a non-inherited field can use the same name as an inherited field.
If the non-inherited field has been named same as the inherited field - both the fields should continue to get displayed, both the inherited field and the non-inherited shall stay in their appropriate locations.
While reconfiguring a non-inherited field with same name as an inherited field, the Data Type (Field Type property under the Field Properties window) should be same as the inherited field. If not, an error needs to be displayed. There are two possibilities:
The user configures the same name in the Field Name property and then changes the Field Type field. If so, the error will be displayed when the user changes the Data Type window and a message should be given saying "Field Type should not be changed when field name is reused from an inherited field. The field type should be <field type value from the inherited field>."
The user configures the Field Name property to have the same name as an inherited field but doesn't get to the Field Type property after that and performs check-in. If so, the error will be displayed when the user changes the Field Name attribute and makes it same as an inherited field and has an incorrect Field Type value. A message will be given saying "Field Type should not be changed when field name is reused from an inherited field. The field type should be <field type value from the inherited field>."
- An inherited field can be cut from the pane.
- If a paste action is executed the new field is a duplicate of the inherited field except for the name of the field.
If the configuror wants to reuse the same name in the non-inheritance space, it should be allowed. The condition for unique name should be checked within the non-inheritance space - meaning, within the non-inherited fields, no two fields can have the same name but a non-inherited field can use the same name as an inherited field.
If the non-inherited field has been named same as the inherited field - both the fields should continue to get displayed, both the inherited field and the non-inherited shall stay in their appropriate locations.
- Upon check in the inherited returns in the position it held before the cut.
- A field's copied from an ancestral product along with its name (irrespective of whether the Display Name is changed in the new field or not) via the Xml Source pane should be allowed and both the inherited field and the non-inherited field should get displayed appropriately in the Fields Pane.
- A field structure from an ancestral product may be copied and checked-in without error.
- Both the the inherited field and the non-inherited field should get displayed appropriately in the Fields Pane.
- Note: In the case of a user reconfiguring the Data Type in the XML Source pane, we will not be validating this. This will be kept out of scope for this enhancement and release since we do not validate incorrect configurations (except invalid XML) when made from XML Source pane since we do not parse the XML Data and perform validations. This will be taken with a larger enhancement for adding validations to the XML Source pane.
Plan Fields behavior when a Field is reconfigured with the same FieldName.
- When the same field name is reconfigured - only the non-inherited field is applicable when used in the context of this plan - in Plan Data, as Plan field in the context of this Plan. No change to this behavior except what is explained in terms of display changes in the Fields Pane
.
